Movement between multiple views

ABSTRACT

The present aspects relate to swift movement between multiple pages or views. Electronic devices may be limited in readily moving between two or more pages or views within an application process. For example, to move between multiple pages or views, an electronic device may receive a single input for movement between one page or view and another page or view. However, the present aspects enable an electronic device to move between two or more pages in response to receiving a single input representing, for instance, a contact on a touch-sensitive surface of the electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/171,932, entitled “MOVEMENT BETWEEN MULTIPLE VIEWS,” filed Jun.5, 2015, the content of which is hereby incorporated by reference in itsentirety for all purposes.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for movement between multiple views.

BACKGROUND

Electronic devices may display content of an application process inmultiple pages or views. As such, electronic devices may display eachpage as a user moves from one page or view to another, for example, toview various forms of the content. However, electronic devices may belimited in moving readily between multiple pages or views.

BRIEF SUMMARY

Some techniques for movement between multiple views using electronicdevices, however, are generally cumbersome and inefficient. For example,existing techniques may use a complex and time-consuming user interface,which may include multiple contact inputs, key presses or keystrokes.Existing techniques require more time than necessary, detracting fromthe user's experience, and wasting user time and device energy. Thislatter consideration may be particularly important in battery-operateddevices.

Accordingly, the present embodiments provide for electronic devices withfaster, more efficient methods and interfaces for movement betweenmultiple views. Such methods and interfaces optionally complement orreplace other methods for movement between multiple views. Such methodsand interfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

The present embodiments provide for methods and/or interfaces that alsoreduce the number of unnecessary, extraneous, repetitive, and/orredundant inputs, and may create a faster and more efficient userinterface arrangement, which may reduce the number of required inputs,reduce processing power, and reduce the amount of time for which userinterfaces need to be displayed in order for desired functions to beaccessed and carried out.

In accordance with some embodiments, a method is performed at anelectronic device including a display and a touch-sensitive surface:displaying, on the display, a first view in a sequence of views; whiledisplaying the first view, receiving an input corresponding to amovement of a contact on the touch-sensitive surface from a firstposition to a second position; while continuing to detect the contact onthe touch-sensitive surface, and in response to receiving the input,preparing to perform a view navigation operation, wherein: in accordancewith a determination that the movement of the contact meets single-viewnavigation criteria, the view navigation operation includes navigatingfrom the first view to a second view that is adjacent to the first viewin the sequence of views; and in accordance with a determination thatthe movement of the contact meets multi-view navigation criteria, theview navigation operation includes navigating from the first view to athird view that is separated from the first view by one or more views inthe sequence of views.

In accordance with some embodiments, a non-transitory computer-readablestorage medium comprises one or more programs for execution by one ormore processors of an electronic device, the one or more programsincluding instructions which, when executed by the one or moreprocessors, cause the electronic device to: display a first view in asequence of views; while displaying the first view, receive an inputcorresponding to a movement of a contact on a touch-sensitive surfacefrom a first position to a second position; while continuing to detectthe contact on the touch-sensitive surface, and in response to receivingthe input, prepare to perform a view navigation operation, wherein: inaccordance with a determination that the movement of the contact meetssingle-view navigation criteria, the view navigation operation includesnavigation from the first view to a second view that is adjacent to thefirst view in the sequence of views; and in accordance with adetermination that the movement of the contact meets multi-viewnavigation criteria, the view navigation operation includes navigationfrom the first view to a third view that is separated from the firstview by one or more views in the sequence of views.

In accordance with some embodiments, an electronic device comprises: oneor more processors; memory; a display and a touch-sensitive surface eachcoupled to the one or more processors and memory; and one or moreprograms stored in memory, the one or more programs includinginstructions for: displaying, on the display, a first view in a sequenceof views; while displaying the first view, receiving an inputcorresponding to a movement of a contact on the touch-sensitive surfacefrom a first position to a second position; while continuing to detectthe contact on the touch-sensitive surface, and in response to receivingthe input, preparing to perform a view navigation operation, wherein: inaccordance with a determination that the movement of the contact meetssingle-view navigation criteria, the view navigation operation includesnavigating from the first view to a second view that is adjacent to thefirst view in the sequence of views; and in accordance with adetermination that the movement of the contact meets multi-viewnavigation criteria, the view navigation operation includes navigatingfrom the first view to a third view that is separated from the firstview by one or more views in the sequence of views.

Thus, devices are provided with faster, more efficient methods andinterfaces for movement between multiple views, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods formovement between multiple views.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6A illustrates example user interfaces for backward movementbetween multiple views in accordance with some embodiments.

FIG. 6B illustrates example user interfaces for forward movement betweenmultiple views in accordance with some embodiments.

FIG. 6C illustrates example user interfaces for single-view movementbetween multiple views in accordance with some embodiments.

FIG. 6D illustrates example user interfaces for multi-view movementbetween multiple views in accordance with some embodiments.

FIG. 6E illustrates example user interfaces for disengaging thepreparation of backward movement between multiple views in accordancewith some embodiments.

FIG. 6F illustrates example user interfaces for single-view movementbetween multiple views in accordance with some embodiments.

FIG. 6G illustrates example user interfaces for forward movement betweenmultiple views in accordance with some embodiments.

FIG. 6H illustrates example user interfaces for disengaging thepreparation of forward movement between multiple views in accordancewith some embodiments.

FIG. 6I is a chart diagram illustrating a history of movement betweenviews in accordance with some embodiments.

FIG. 7 is a flow diagram of an example process of moving betweenmultiple views in accordance with some embodiments.

FIG. 8 is a functional block diagram in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

The present embodiments generally relate to readily moving betweenmultiple views. Specifically, an electronic device enables a user tomove from one view or page to another view or page within an applicationprocess. For example, an electronic device such as a mobile deviceenables a user to navigate between views or pages within a web browser.In one instance, a user begins at a first page of a first website andeventually navigates to a third page of the first website. However, theuser may then wish to return to the first page from the third page. Theforegoing example should not be construed as limiting, and in someembodiments, the user may navigate from a third page to a first page,and then wish to advance back to the third page.

In some embodiments, the electronic device may receive at least twoinputs corresponding to two contacts or manipulations by the userdesiring to return to the first page. In other words, the electronicdevice navigates to the second page from the third page, prior tonavigating from the second page to the first page. However, suchnavigating may require the user to enter or engage the electronic devicein a repetitious manner in order to navigate each intermediate view orpage individually until the desired view or page is displayed. As such,it would desirable for electronic devices to forgo display or navigationof the second page, and to move from the third page to the first page.As such, the present embodiments enables navigation from a first page orview to a third page or view that is separated from the first page orview by one or more views or pages.

Accordingly, there is a need for electronic devices that provideefficient methods and interfaces for movement between multiple views.Such techniques can reduce the cognitive and/or physical burden on auser navigating between multiple views, thereby enhancing efficiency andproductivity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for movement betweenmultiple views. FIGS. 6A-6G illustrate exemplary user interfaces forreadily moving between multiple views. The user interfaces in thefigures are also used to illustrate the processes described below,including the process in FIG. 7.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” can optionally be construed to mean “when” or “upon” or“in response to determining” or “in response to detecting,” depending onthe context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” can optionally be construed tomean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device can optionally support a variety of applications, such as oneor more of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit.area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 can optionally include one or more computer-readable storagemediums. The computer-readable storage mediums can optionally betangible and non-transitory. Memory 102 can optionally includehigh-speed random access memory and can optionally also includenon-volatile memory, such as one or more magnetic disk storage devices,flash memory devices, or other non-volatile solid-state memory devices.Memory controller 122 can optionally control access to memory 102 byother components of device 100. Executable instructions for performingthese functions are, optionally, included in a transitorycomputer-readable storage medium or other computer program productconfigured for execution by one or more processors.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 can optionally beimplemented on a single chip, such as chip 104. In some embodiments,they can optionally be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data can optionally beretrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output can optionallyinclude graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output can optionally correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 can optionally use LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiescan optionally be used in some embodiments. Touch screen 112 and displaycontroller 156 can optionally detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with touch screen 112. In an exemplaryembodiment, projected mutual capacitance sensing technology is used,such as that found in the iPhone® and iPod Touch® from Apple Inc. ofCupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 canoptionally be analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 canoptionally be as described in the following applications: (1) U.S.patent application Ser. No. 11/381,313, “Multipoint Touch SurfaceController,” filed May 2, 2006; (2) U.S. patent application Ser. No.10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patentapplication Ser. No. 10/903,964, “Gestures For Touch Sensitive InputDevices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No.11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31,2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-BasedGraphical User Interfaces For Touch Sensitive Input Devices,” filed Jan.18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “VirtualInput Device Placement On A Touch Screen User Interface,” filed Sep. 16,2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of AComputer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S.patent application Ser. No. 11/228,737, “Activating Virtual Keys Of ATouch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patentapplication Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,”filed Mar. 3, 2006. All of these applications are incorporated byreference herein in their entirety.

Touch screen 112 can optionally have a video resolution in excess of 100dpi. In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user can optionally make contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100 canoptionally include a touchpad (not shown) for activating or deactivatingparticular functions. In some embodiments, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad can optionally be atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 can optionally include a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 can optionally also include one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 can optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 can optionallycapture still images or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch screen display 112 onthe front of the device so that the touch screen display can optionallybe used as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image can optionally be obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 can optionally be used along with the touch screendisplay for both video conferencing and still and/or video imageacquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 can optionally also include one or more proximity sensors166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface118. Alternately, proximity sensor 166 can optionally be coupled toinput controller 160 in I/O subsystem 106. Proximity sensor 166 canoptionally perform as described in U.S. patent application Ser. No.11/241,839, “Proximity Detector In Handheld Device”; Ser. No.11/240,788, “Proximity Detector In Handheld Device”; Ser. No.11/620,702, “Using Ambient Light Sensor To Augment Proximity SensorOutput”; Ser. No. 11/586,862, “Automated Response To And Sensing Of UserActivity In Portable Devices”; and Ser. No. 11/638,251, “Methods AndSystems For Automatic Configuration Of Peripherals,” which are herebyincorporated by reference in their entirety. In some embodiments, theproximity sensor turns off and disables touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 can optionally also include one or more accelerometers 168.FIG. 1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 can optionally be coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 can optionallyperform as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which can optionally be a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 can optionally include the following modules (or setsof instructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which can optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that can optionally be stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 can optionally be used to manage an addressbook or contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 can optionally be used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication can optionally use any of a pluralityof communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages can optionally include graphics, photos, audio files,video files and/or other attachments as are supported in an MMS and/oran Enhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that can optionally be downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150can optionally be used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154can optionally be used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules can optionally be combined orotherwise rearranged in various embodiments. For example, video playermodule can optionally be combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 can optionally store a subset of the modules anddata structures identified above. Furthermore, memory 102 can optionallystore additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some embodiments, the menubutton is a physical push button or other physical input control deviceinstead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In some embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected can optionally be calledthe hit view, and the set of events that are recognized as proper inputscan optionally be determined based, at least in part, on the hit view ofthe initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In some embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In some embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In someembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In some embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 can optionally utilize or call dataupdater 176, object updater 177, or GUI updater 178 to update theapplication internal state 192. Alternatively, one or more of theapplication views 191 include one or more respective event handlers 190.Also, in some embodiments, one or more of data updater 176, objectupdater 177, and GUI updater 178 are included in a respectiveapplication view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which can optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation can optionally also include speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In some embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 can optionally also include one or more physical buttons,such as “home” or menu button 204. As described previously, menu button204 can optionally be used to navigate to any application 136 in a setof applications that can optionally be executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 can optionally be storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules can optionally be combined or otherwiserearranged in various embodiments. In some embodiments, memory 370 canoptionally store a subset of the modules and data structures identifiedabove. Furthermore, memory 370 can optionally store additional modulesand data structures not described above.

Attention is now directed towards embodiments of user interfaces thatcan optionally be implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces can optionally be implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 can optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) canoptionally have one or more intensity sensors for detecting intensity ofcontacts (e.g., touches) being applied. The one or more intensitysensors of touch screen 504 (or the touch-sensitive surface) can provideoutput data that represents the intensity of touches. The user interfaceof device 500 can respond to touches based on their intensity, meaningthat touches of different intensities can invoke different userinterface operations on device 500.

Techniques for detecting and processing touch intensity are found, forexample, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 can optionally be a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508can optionally be a button, in some examples.

Input mechanism 508 can optionally be a microphone, in some examples.Personal electronic device 500 can include various sensors, such as GPSsensor 532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 702-712 (FIG. 7). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.Executable instructions for performing these functions are, optionally,included in a transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that can be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) each canoptionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds canoptionally include a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location canoptionally be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmcan optionally be applied to the intensities of the swipe contact priorto determining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input, includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIGS. 6A and 6B illustrate example user interfaces for movement betweenmultiple views in accordance with some embodiments. In one embodiment,FIG. 6A illustrates example user interfaces for backward movementbetween multiple views or pages. In some embodiment, FIG. 6B illustratesexample user interfaces for forward movement between multiple views orpages.

Referring to FIG. 6A, for example, an electronic device 600 includesdisplay 602 and touch-sensitive surface 604. In some embodiments,electronic device 600 can optionally be the same as or similar toportable multifunction device 100 (FIG. 1), multifunction device 300(FIG. 3), and/or personal electronic device 500 (FIG. 5). Further, insome embodiments, display 602 and touch-sensitive surface 604, eitherindividually or in combination, can optionally be the same as or similarto one touch-sensitive display system 112 (FIG. 1), display 340 (FIG.3), touchpad 355 (FIG. 3), and/or touch-sensitive display screen 504(FIG. 5).

Electronic device 600 is configured to navigate to and/or from one ormore views displayed on display 602, and in response to one or moreinputs received on touch-sensitive surface 604. In some embodiments,electronic device 600 initially displays, on display 602, a first view606. As shown on FIG. 6A, the first view 606 can optionally be indicatedas number “1”. In some embodiments, a view can optionally be orotherwise include a set of content displayed on display 602. Forexample, a view can be one or more of a webpage, a page of an electronicbook/journal/magazine, and/or a page of an application process. Forexample, the first view 606 can optionally be any page of a news readerapplication process. In another example, the first view 606 canoptionally be a homepage of a website. In yet another example, the firstview 606 can optionally be any page of an electronic book. It should beunderstood that first view 606 is not limited to the foregoing examples.

In some embodiments, electronic device 600 then displays a second view608, which is indicated as number “2”, upon receiving an inputrepresenting or otherwise corresponding to a selection of second view608. In an aspect, electronic device 600 displays second view 608 inresponse to a selection of an affordance or a series of affordances. Forinstance, first view 606 is a webpage including one or more affordances(e.g., hyperlinks) to other webpages within the same or differentdomain. In another example, first view 606 is a first page of a newreader application process including one or more page movementaffordances (e.g., forward and backward affordances). As such, uponselection of one of the affordances from the one or more affordances(e.g., forward affordance), or other user input, electronic device 600ceases display of first view 606 and display second view 608. In otherwords, electronic device 600 replaces, on display 602, first view 606with second view 608. In some embodiments, electronic device isconfigured to partially replace first view 606 with second view 608,such that a portion of first view 606 visible, usable for quicknavigation back to first view 606 from second view 608, and even withuser finger 620 not touching the device.

Additionally, electronic device 600 displays, on display 602, third view610, which is indicated as number “3”, upon receiving an inputrepresenting or otherwise corresponding to of third view 610. In anaspect, electronic device 600 displays third view 610 in response to aselection of an affordance or a series of affordances. For example,second view 608 is a webpage including one or more affordances (e.g.,hyperlinks) to other webpages within the same or different domain. Inanother example, second view 608 is a second page of a new readerapplication process including one or more page movement affordances(e.g., forward and backward affordances). As such, upon selection of oneof the affordances from the one or more affordances (e.g., forwardaffordance), or other user input, electronic device 600 ceases displayof second view 608 and display third view 610. In other words,electronic device 600 replaces, on display 602, second view 608 withthird view 610.

In some embodiments, after traversing or navigating from second view 608to third view 610, a user may desire to return to first view 606 fromthird view 610, without having to traverse or navigate initially tosecond view 608 before eventually returning to first view 606. In otherwords, a user may desire to navigate between multiple views withouthaving to navigate or perform additional repetitive gestures or contactswith touch-sensitive surface 604 for navigating or traversingintermediate views before reaching the desired view (e.g., first view606). As such, electronic device 600 prepares to perform a multi-viewnavigation operation and subsequently navigates between multiple viewsbased on or otherwise in response to receiving a multi-view navigationinput.

For instance, while displaying third view 610, electronic device 600receives an input from a user on touch-sensitive surface 604. Electronicdevice 600 determines the type or pattern of the received input. Thatis, in some embodiments, electronic device 600 receives or otherwisedetects a single-view navigation input. For example, the single-viewnavigation input corresponds to a detection of a horizontal swipegesture across touch-sensitive surface 604 (or a swipe in apredominantly horizontal direction). Accordingly, electronic device 600prepares to perform a single-view navigation operation and subsequentlyreturns or navigates from third view 610 to second view 608 (e.g.,“single-view navigation”).

In some embodiments, electronic device 600 receives or otherwise detectsa multi-view navigation input and enables navigation between multipleviews. For instance, the multi-view navigation input corresponds to adetection of a horizontal swipe gesture that decelerates proximate anedge of the touch-sensitive surface 604. As such, electronic device 600returns or navigates from third view 610 to first view 606 (e.g.,“multi-view navigation”). The present embodiments are not limited tonavigating between third view 610 and first view 606 with respect tomulti-view navigation. That is, electronic device 600 navigates from acurrent view to a previous view, separated by one or more views.Accordingly, in the examples illustrated in FIG. 6A, third view 610 isseparated from first view 606 by one or more views (e.g., includingsecond view 608). As such, the present embodiments enable electronicdevice 600 to navigate between multiple views based on or in response toreceiving a single input.

Referring to FIG. 6B, example user interfaces are illustrated forforward movement following a series or sequence of backward movementsbetween multiple views in accordance with some embodiments. For example,electronic device 600 initially displays third view 610. In response toreceiving an input on touch-sensitive surface 604, electronic device 600navigates to from the third view 610, which is higher or succeeds otherviews in a sequence of views, to second view 608. In other words,electronic device 600 navigates in a backward manner with respect to asequence of views from a higher order view (e.g., third view 610) to alower order view (e.g., second view 608). In some embodiments, a user ofelectronic device 600 may desire to return or move back from third view610 to second view 608.

Further, electronic device 600 navigates from second view 608 to firstview 606. In some embodiments, the second view 608 is higher or succeedsthe first view 606 in the sequence of views, yet is lower or precedesthe third view 610 in the sequence of views. For instance, a user mayagain desire to return or move back from second view 608 to first view606, which precedes the second view 608. In other words, electronicdevice 600 navigates in a backward manner with respect to a sequence ofviews from a higher order view (e.g., second view 608) to a lower orderview (e.g., first view 606).

Following navigation from third view 610 to first view 606, which isseparated by one or more views (e.g., second view 608), electronicdevice 600 determines a type or pattern of input corresponding to aforward movement or navigation, and received on touch-sensitive surface604 while displaying first view 606. That is, following a number ofsuccessive movements (e.g., two or more) from one view to another view(e.g., from third view 610 to first view 606 via second view 608) in abackward or preceding manner in the sequence of views, electronic device600 prepares to perform a view navigation operation and subsequentlymove or navigate in a forward manner in the sequence of views to one ofthe second view 608 or the third view 610. Specifically, electronicdevice 600 navigates to prepare to perform a single-view navigationoperation and subsequently navigate to second view 608 in response toreceiving an input corresponding to single-view navigation. However,electronic device 600 prepares to perform a multi-view navigationoperation and subsequently navigate to third view 610, which isseparated from first view 606 by one or more views, in response toreceiving an input corresponding to multi-view navigation.

FIG. 6C illustrates example user interfaces for movement between viewsin accordance with some embodiments, for example, the embodimentsdescribed with respect to the preparation of performing a single-viewnavigation operation, which corresponds to navigation from third view610 to second view 608 in FIG. 6A. In some embodiments, the movement ornavigation illustrated and described in FIG. 6C is referred to asbackward movement or navigation in a sequence of views, where the secondview 608 precedes the third view 610.

FIG. 6C illustrates a non-limiting series of user interfacesillustrating navigation between multiple views of a single-viewoperation. For example, at user interface 622, electronic device 600displays, on display 602, third view 610. In some embodiments, firstview 606, second view 608, and third view 610 are each a respective viewin a sequence of views. For example, third view 610 is a third page ofan application process (e.g., news reader application process). Further,the sequence of views is a series or hierarchy. As such, each respectiveview is positioned or arranged based on a time domain parameter and/or abrowser history (as described further with regard to FIG. 6I).

While displaying user interface 622, electronic device 600 receives aninput corresponding to a movement of a contact 682 on thetouch-sensitive surface 604. For example, the movement of the contact682 is representative of a user finger 620 in contact with and movingacross the touch-sensitive surface 604 in a direction corresponding to adesired navigation between views. In other words, electronic device 600detects a movement of an object having a horizontal component such as,but not limited to, a user finger 620 from a location proximate one edgeof the display to a location proximate another edge.

In response to receiving the input corresponding to the movement of thecontact 682 (e.g., corresponding to user finger 620) on touch-sensitivesurface 604, electronic device 600, at user interface 624, displays aview navigation or transition animation whereby a portion of the thirdview 310 is displayed on display 602, as well as a portion of the secondview 608, which is a view preceding the third view 610 by one view in asequence of views. As such, at user interface 624, electronic device 600prepares to perform a single-view navigation operation, which includesor otherwise corresponds to a movement or navigation from third view 610to second view 608.

It should be understood that the dashed lines indicate a view or pageseparation. For example, at user interface 624, the dashed line in themiddle of display 602 indicates a portion of display 602 displayingsecond view 608 and another portion of display 602 displaying third view610. Additionally, the dashed line indicating distinct views and/or aboundary between views can be optionally displayed on display 602 invarious forms (e.g., dashed, solid, etc.). At user interface 624,electronic device 600 detects liftoff of the contact 682 (e.g.,corresponding to user finger 620), ceases display of the preparedsingle-view navigation animation, and displays second view 608 at userinterface 630.

FIG. 6D illustrates example user interfaces for movement betweenmultiple views in accordance with some embodiments, for example, theembodiments described with respect to the preparation of performing amulti-view navigation operation, which corresponds to navigation fromthird view 610 to first view 606 in FIG. 6A. In some embodiments, themovement or navigation illustrated and described in FIG. 6D is referredto as backward movement or navigation in a sequence of views, where thefirst view 606 precedes the third view 610 by one or more views.

In particular, FIG. 6D includes a non-limiting series of user interfacesillustrating navigation between multiple views. For example, at userinterface 622, electronic device 600 displays, on display 602, thirdview 610. In some embodiments, first view 606, second view 608, andthird view 610 are each a respective view in a sequence of views. Forexample, third view 610 is a third page of an application process (e.g.,news reader application process). Further, the sequence of views is aseries or hierarchy. As such, each respective view is positioned orarranged based on a time domain parameter and/or a browser history (asdescribed further with regard to FIG. 6I).

While displaying user interface 622, electronic device 600 receives aninput corresponding to a movement of a contact 682 on thetouch-sensitive surface. For example, the movement of the contact 682 isrepresentative of a user finger 620 in contact with and moving acrossthe touch-sensitive surface 604 in a direction corresponding to adesired navigation between views. In other words, electronic device 600detects a movement of an object having a horizontal component such as,but not limited to, a user finger 620 from a location proximate one edgeof the display to a location proximate another edge.

In response to receiving the input corresponding to the movement of thecontact 682 (e.g., corresponding to user finger 620) on touch-sensitivesurface 604, electronic device 600, at user interface 624, displays aview navigation or transition animation whereby a portion of the thirdview 310 is displayed on display 602, as well as a portion of the secondview 608, which is a view preceding the third view 610 by one view in asequence of views. It should be understood that the dashed linesindicate a view or page separation. For example, at user interface 624,the dashed line in the middle of display 602 indicates a portion ofdisplay 602 displaying second view 608 and another portion of display602 displaying third view 610. Additionally, the dashed line indicatingdistinct views and/or a boundary between views is optionally displayedon display 602 in various forms (e.g., dashed, solid, etc.).

At user interface 626, the user may desire to move between more than oneview in the sequence of views. That is, the user may desire to return tothe first view 606 from the third view 610 without navigating to, orhaving fully displayed, second view 608. As such, at user interface 626,electronic device 600 detects movement of the contact 682 on thetouch-sensitive surface 604 from the first position at user interface622 to a second position at user interface 626. Accordingly, electronicdevice 600, prepares performance of a view navigation operation (e.g.,multi-view navigation) while continuing to detect the contact 682 on thetouch-sensitive surface 604 (e.g., corresponding to contact by userfinger 620 at second position).

In some embodiments, electronic device 600 navigates from the third view610 to second view 608 that is adjacent to the third view 610 in thesequence of views in accordance with a determination that the movementof the contact 682 meets single-view navigation criteria. For instance,electronic device 600 navigates from the third view 310 directly to thefirst view 606 that is separated from the third view 610 by one or moreviews in the sequence of views (e.g., including the second view 608) inaccordance with a determination that the movement of the contact 682(e.g., corresponding to user finger 620) meets multi-view navigationcriteria.

In some embodiments, electronic device 600 determines that movement ofthe contact 682 has decelerated below a threshold level at a multi-viewregion of the touch-sensitive surface 604. As such, electronic device600 displays, at user interface 628, first view 606 on display 602.Otherwise, at user interface 624, electronic device 600 determines thatmovement of the contact 682 (e.g., corresponding to user finger 620) onthe touch-sensitive surface 604 meets single-view navigation criteria,and navigates from the third view 610 to the second view 608. In suchexample, the third view 610 precedes the first view 606 in the sequenceof views. As such, third view 610 is the last view in the sequence ofviews, whereas the first view 606 is the initial view in the sequence.In some embodiments, third view 610 is the initial view in the sequenceof views, whereas the first view 606 is the last view in the sequence.

In some embodiments, touch-sensitive surface 604 includes a first region660 and a second region 662 separate or distinct from the first region.For example, the first region 660 corresponds to a single viewnavigation region where movement of the contact 682 from a firstlocation to a second location within the single view navigation regionand an end of the input (e.g., subsequent liftoff of the contact 682)triggers (e.g., causes the electronic device 600 to perform) asingle-view navigation operation (e.g., moving from third view 610 tosecond view 608). Further, second region 662 corresponds to a multi-viewnavigation region where movement of the contact 682 from a firstlocation to a second location within or to the multi-view navigationregion and an end of the input (e.g., subsequent liftoff of the contact682) therein triggers (e.g., causes the device to perform) a multi-viewnavigation operation (e.g., moving from third view 610 to first view606).

Electronic device 600 determines whether the movement of the contact 682meets single-view navigation criteria or multi-view navigation criteriabased on one or more embodiments. In some embodiments, for example, thesingle-view navigation criteria includes a determination by theelectronic device 600 that the multi-view navigation criteria is notmet. Further, the single-view navigation criteria includes adetermination by electronic device 600 that the first input correspondsto movement only in the first region 660. In some embodiments, thesingle-view navigation criteria includes determining that the firstinput corresponds to a swipe from an edge of the touch-sensitive surface604 within the first region 660. For instance, electronic device 600determines that a detected contact 682 (e.g., corresponding to userfinger 620, which corresponds to or otherwise be in contact withtouch-sensitive surface 604), engages in a swipe gesture from a leftedge of touch-sensitive surface 604 towards the opposite edge and withinthe first region 660 (e.g., as shown in user interface 624).

Additionally, in some embodiments, electronic device 600 determines thatthe movement of the contact 682 (e.g., the contact corresponding to userfinger 620) meets multi-view navigation criteria based on adetermination that the first input corresponds to a swipe that starts inthe first region and transitions into the second region. For example,user finger 620 begins in first region 660 (e.g., user interface 622),continues movement through first region 660 (e.g., user interface 624),and transitions in to second region 662 (e.g., user interface 626).

In some embodiments, the multi-view navigation criteria includes adetermination by electronic device 600 that the first input correspondsto a contact 682 that decelerates within the second region 662. In someembodiments, the contact 682 decelerates by at least a minimum amountwithin the second region 662. Thus, in some embodiments, electronicdevice 600 detects whether the contact 682 (e.g., via user finger)decelerates to a value below a threshold within the second region 662.

In some embodiments, the multi-view navigation criteria includes adetermination at electronic device 600 that the contact 682 has remainedin the second region 662 of the touch-sensitive surface 604 for a periodof time meeting or exceeding a time threshold. For instance, a timetracks the time of the contact 682 (e.g., swipe gesture by user finger620) in each region. As such, the time value associated with a length inthe second region 662 is compared to a multi-view navigation threshold.In some embodiments, the multi-view navigation threshold is a time valueselected in a range of 1 millisecond to 3 seconds.

Further, electronic device 600, at user interface 626, receives a secondinput corresponding to liftoff of the contact 682 from thetouch-sensitive surface 604, after preparing to perform the viewnavigation operation. For example, at user interface 626, a userliftoffs user finger 620 from touch-sensitive surface 604 afterelectronic device 600 prepares to perform the multi-view navigationoperation. Accordingly, electronic device 600 performs the viewnavigation operation (e.g., multi-view navigation operation) in responseto receiving the second input (e.g., liftoff of the user finger 620 fromtouch-sensitive surface 604).

In some embodiments, electronic device 600 displays and/or animate astacking representation of views while detecting the movement of thecontact 682 on the touch-sensitive surface 604 from the first positionto the second position (e.g., when the multi-view navigation criteriawill be satisfied upon liftoff at the current location of the contact682, so as to indicate to the user that a multi-view navigation thatliftoff of the contact 682 at the current location will cause amulti-view navigation operation to be performed, rather than asingle-view navigation operation). For example, as the user swipesacross touch-sensitive surface 604, a stacked representation of theviews is displayed on display 602. As shown at user interface 626, thestacked representation includes second view 608 and third view 610 ontop of or adjacent to second view 608.

Specifically, electronic device 600 displays a stacked viewrepresentation of a plurality of portions (e.g., a portion of secondview 608 and third view 610) each corresponding to a view of the one ormore views separating the first view 606 from the third view 610. Thestacked view representation is a dynamic image of a plurality of viewsthat is formed of the views between the first view 606 and the thirdview 610, and including the third view 610. The display of the stackedview representation is, optionally, displayed in accordance with adetermination that the movement of the contact 682 (e.g., correspondingto user finger 620) meets multi-view navigation criteria.

In some embodiments, the first portion represents the first view 606 ofthe one or more views separating the first view 606 from the third view610. Additionally, the second portion represents a second view 608 ofthe one or more views separating the first view 606 from the third view610, and different than the first view 606 of the one or more viewsseparating the first view 606 from the third view 610. In someembodiments, electronic device 600 displays the first portion of thestacked view representation prior to displaying the second portion ofthe stacked view representation.

In some embodiments, the number of portions in the plurality of portionsis less than the number of views of the one or more views separating thefirst view 606 from the third view 610. Further, the first portion andthe second portion of the stacked view representation is displayed at anangle with respect to a vertical axis. For example, the stacked viewrepresentation is initially displayed parallel to the vertical axis andgradually rotates as the user continues to swipe through the secondregion 662. In some embodiments, the stacked view representationcontinues to be displayed parallel to the vertical axis as theelectronic device receives the input from the first region 660 andthrough the second region 662 (e.g., corresponding to user swipingthrough second region 662).

FIG. 6E illustrates example user interfaces for disengaging thepreparation of movement between multiple views in accordance with someembodiments. For example, the embodiments illustrated and described withrespect to FIG. 6E begins at user interface 628, as shown in FIG. 6D.Specifically, electronic device 600 ceases display of the stacked viewrepresentation including second view 608 and third view 610 at userinterface 628 based on, for example, movement of the contact 682 (e.g.,corresponding to user finger 620) out of the second region 662 and intothe first region 660. By disengaging from preparation of the multi-viewnavigation operation, the user returns to third view 610 (correspondingto user interface 622 of FIG. 6C).

In some embodiments, electronic device 600, after or during display ofthe stacked view representation at user interface 628, determineswhether a stacked view representation deconstruction criteria is met.Accordingly, electronic device 600 ceases to display the stacked viewrepresentation in user interface 632 in accordance with a determinationthat the stacked view representation deconstruction criteria is met. Forexample, in some embodiments, electronic device 600 ceases to displaythe second portion (e.g., second view 608) of the stacked viewrepresentation prior to ceasing to display the first portion (e.g.,third view 610) of the stacked view representation.

In some embodiments, the stacked view representation is deconstructedbased on a determination at electronic device 600 that movement of thecontact 682 meets the single-view navigation criteria (e.g., detectingmovement of user finger 620 back into first region 660). Additionally,at user interface 632, electronic device 600 displays second view 608 inresponse to a liftoff of contact 682 during single-view navigation.Otherwise, electronic device 600 displays third view 610 when neithersingle-view navigation criteria nor multi-view navigation criteria ismet. It should be understood that the embodiments described herein withrespect to FIGS. 6A-6E can optionally apply to the embodiments of FIG.6F-6H.

FIG. 6F illustrates a non-limiting series of user interfacesillustrating navigation between multiple views of a single-viewoperation. For example, at user interface 640, electronic device 600displays, on display 602, first view 606. Specifically, electronicdevice 600 navigates to second view 608 based on a determination thatthe movement of the contact 682 (e.g., corresponding to user finger 620)meets single-view navigation criteria. For example, as the user movesuser finger 620 across touch-sensitive surface 604 while display 602displays first view 606 at user interface 640, electronic device 600prepares to perform a view navigation operation based on the viewnavigation criteria described herein (e.g., single-view navigationcriteria).

Further, at user interface 642, electronic device 600 displays firstview 608 and second view 608 adjacent the first view 606. At userinterface 642, electronic device 600 determines that single-viewnavigation criteria is met, and displays, on display 602, arepresentation including first view 606 and second view 608. Uponliftoff of the contact 682 (e.g., corresponding to user finger 620) fromtouch-sensitive surface 604, electronic device 600 navigates forward to,and displays the second view 608.

FIG. 6G illustrates example user interfaces for movement betweenmultiple views in accordance with some embodiments, for example, theembodiments described with respect to the preparation of performing amulti-view navigation operation, which corresponds to navigation fromfirst view 606 to third view 610 in FIG. 6B. In some embodiments, themovement or navigation illustrated and described in FIG. 6G is referredto as forward movement or navigation in a sequence of views, where thethird view 610 succeeds the first view 606 by one or more views.

Specifically, electronic device 600 navigates to third view 610 based ona determination that the movement of the contact 682 (e.g.,corresponding to user finger 620) meets multi-view navigation criteria.For example, as the user moves user finger 620 across touch-sensitivesurface 604 while display 602 displays first view 606 at user interface640, electronic device 600 prepares to perform a view navigationoperation based on the view navigation criteria described herein (e.g.,single-view navigation criteria and multi-view navigation criteria).

Further, at user interface 642, electronic device 600 displays firstview 608 and second view 608 adjacent the first view 606. At userinterface 644, electronic device 600 determines that multi-viewnavigation criteria is met, and displays, on display 602, a stacked viewrepresentation including first view 606 and second view 608. In suchexample, the third view 610 succeeds the first view 606 in the sequenceof views. Upon liftoff of the contact 682 (e.g., corresponding to userfinger 620) from touch-sensitive surface 604, electronic device 600navigates forward to, and displays the third view 610.

FIG. 6H illustrates example user interfaces for disengaging thepreparation of movement between multiple views in accordance with someembodiments. Specifically, electronic device 600 ceases display of thestacked view representation including second view 608 and third view 610at user interface 630 based on, for example, movement of the content(e.g., corresponding to user finger 620) out of the second region 662and into the first region 660. For example, at user interface 650, astacked view representation is displayed on display 602. At userinterface 652, electronic device 600 ceases display of the stacked viewrepresentation based on a determination that single-view navigationcriteria is met. Further, electronic device 600 displays second view 608in response to detecting a liftoff of contact 682 (e.g., correspondingto user finger 620) from touch-sensitive surface 604. Otherwise,electronic device 600 displays first view 606 when neither single-viewnavigation criteria nor multi-view navigation criteria is met.

FIG. 6I is a chart diagram 680 illustrating a history and/or pattern ofmovement between views in accordance with some embodiments. Chart 680includes a history axis and a time axis. Further, chart 680 displays aplot of view movement through time at electronic device 600. In someembodiments, the views are associated with one or more applicationprocesses. In other words, the views are associated with or correspondto a single application process (e.g., news reader application process),or is associated with or correspond to two or more application process(e.g., news reader application process and web browser applicationprocess).

As shown in FIG. 6I, as a user navigates from one view to another view,electronic device 600 records or stores a history of the view movement.For example, the electronic device 600 navigates, in response to userinput, from a first view 606 to a second view, and subsequently to athird view 610. Electronic device 600 then returns to second view 608from third view 610. In some embodiments, first view 606 is identifiedas, or determined to be anchor view, which is a view to which electronicdevice 600 navigates to upon determining that multi-view navigationcriteria is met.

Further, chart 680 includes a movement from second view 608 to fourthview 666, which can optionally be a view not associated with the firstsequence of views including the first view 606, second view 608, andthird view 610. That is, in one example, fourth view 666 is associatedwith an application process different from the first sequence of views.In some embodiments, the fourth view is associated with a differentdomain name within a web browser application process. In someembodiment, fourth view 666 is associated with a different chapter fromthe first sequence of views in a book reader application process. Assuch, fourth view 666 is part of a second sequence of views.Additionally, as evidenced from FIG. 6I, fourth view 666 is identifiedas, or determined to be the anchor view for the second sequence ofviews. The second sequence of views includes fifth view 668, sixth view670, seventh view 672, and eighth view 674. The foregoing pattern orhistory of view movement is stored at or remote from electronic device600.

The history is then be analyzed to determine, among other analyticaloutputs, a view separation value. Specifically, electronic device 600determines a view separation value indicative of or corresponding to anumber of views between or separating the first view 606 and the thirdview 610. That is, upon or in conjunction with a determination ofmulti-view navigation criteria, electronic device 600 determines anumber of views separating a current view (e.g., the view currentlydisplayed on display 602 and/or the view displayed while movement ofcontact 682 is detected) and another view. Accordingly, electronicdevice 600 navigates from one view (e.g., first view 606) to anotherview (e.g., third view 610) that is separated from the one view (e.g.,first view 606) by a number of views in the sequence of view that isequal to the view separation value.

In some embodiments, electronic device 600 determines the viewseparation value based on the period time the contact 682 has remainedon a view, or in the second region of the touch-sensitive surface 604.For example, the view navigation operation includes navigating from thethird view 610 to the first view 606 that is separated from the firstview 606 by a number of views in the sequence of views that is equal tothe view separation value. In some embodiments, the third view 610 isseparated from the first view 606 by a predetermined number of views inthe sequence of views.

In some embodiments, electronic device 600 determines view separationvalue and/or the anchor view based on one or more criteria. In oneexample, electronic device 600 determines the view separation valueand/or the anchor view based on a view time parameter. For example, theview time parameter is an amount of time at a particular view. In suchexample, a view time of the first view 606 is greater than a view timeof all other views in the first sequence of views (e.g., second view 608and third view 610).

Further, electronic device 600 determines the view separation valueand/or the anchor view based on the pattern of view movement. Forinstance, electronic device 600 records a number of times a view hasbeen displayed on display 602 to determine a movement pattern. In suchexample, if a user is to navigate to a particular view (e.g. first view606) more often relative to other view (e.g., second view 608 and thirdview 610), electronic device 600 identifies or otherwise indicates thefirst view 606 as an anchor view.

In some embodiments, electronic device 600 determines view separationvalue and/or the anchor view based on an application process category.For instance, each view in a sequence of views is associated with anapplication process. In some embodiments, electronic device 600determines view separation value and/or the anchor view based on a viewhistory. For example, the view history (as shown on chart 680) is storedand analyzed to determine patterns, which uses a longer timeframe thanthe pattern of view movement criteria. Further, electronic device 600uses one or more of the foregoing criteria to determine the viewseparation value and/or the anchor view.

Further, the third view 610 is separated from the first view 606 by apercentage of views in the sequence of views. In some embodiments, thepercentage of views is a predetermined number based on any one of theview time parameter, the pattern of view movement, the applicationprocess category, and/or the view history. In some embodiments, thepercentage of views is initially a default value and is updateddynamically based on movement patterns and/or history of the user.

In accordance with some embodiments, chart 680 demonstrates a nodestructure with respect to the sequences (e.g., first sequence of viewsand second sequence of views). In some embodiments, the sequence ofviews includes part of a hierarchy of views, where the hierarchy ofviews includes one or more nodes. For instance, the sequence of views(e.g., first sequence of views) is a sequence of views within abranching hierarchy of views having one or more nodes corresponding topoints at which the hierarchy branches. In some embodiments, one or moreadditional sequences of views of the hierarchy intersect the firstsequence of views at a node. As such, in some embodiments, the hierarchyof views includes two or more sequence of views.

Chart 680 includes at least a first sequence of views including firstview 606, second view 608, and third view 610. Chart 680 also includessecond sequence of views including fourth view 666, fifth view 668,sixth view 670, and seventh view 672. As such, the hierarchy of viewsincludes the first sequence and the second sequence. In someembodiments, any one of the views in FIG. 6G can optionally be a node inthe hierarchy of views. For example, first view 606 is the first nodeand the fourth view 666 is the second node. In such example, electronicdevice 600 moves from a view in a sequence of views to a node within thesequence. In some embodiments, electronic device 600 moves from one nodeto another node.

FIG. 7 is a flow diagram illustrating a method of movement betweenmultiple views using an electronic device and in accordance with someembodiments. Method 700 can optionally be performed at a device (e.g.,100, 300, and/or 500) with a display. Some operations in method 700 canoptionally be combined, the order of some operations can optionally bechanged, and some operations can optionally be omitted.

As described below, method 700 provides an intuitive way for readilymoving between multiple views or pages. The method reduces the cognitiveand/or physical burden on a user during such movement, thereby creatinga more efficient human-machine interface. For battery-operated computingdevices, enabling a user to move between multiple views faster and moreefficiently conserves power and increases the time between batterycharges.

At block 702, method 700 displays, on the display (e.g., display 602,FIG. 6), a first view in a sequence of views. At block 704, method 700,while displaying the first view (e.g., first view 606, FIG. 6), receivesan input corresponding to a movement of a contact (e.g., contact 682,FIG. 6) on the touch-sensitive surface (e.g., touch-sensitive surface604, FIG. 6) from a first position to a second position. At block 706,method 700, while continuing to detect the contact on thetouch-sensitive surface, and in response to receiving the input,prepares to perform a view navigation operation.

At block 708, method 700 determines whether the movement of the contactmeets single-view navigation criteria or multi-view navigation criteria.At block 710, method 700 includes, in accordance with a determinationthat the movement of the contact meets single-view navigation criteria,the view navigation operation includes navigating from the first view toa second view (e.g., second view 608, FIG. 6) that is adjacent to thefirst view in the sequence of views. At block 712, method 700 includes,in accordance with a determination that the movement of the contactmeets multi-view navigation criteria, the view navigation operationincludes navigating from the first view to a third view (e.g., thirdview 610, FIG. 6) that is separated from the first view by one or moreviews in the sequence of views.

In accordance with some embodiments, method 700 includes, afterpreparing to perform the view navigation operation, receive a secondinput corresponding to liftoff of the contact from the touch-sensitivesurface; in response to receiving the second input, performing the viewnavigation operation.

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the multi-view navigation criteria is not met.

In accordance with some embodiments, the touch-sensitive surfaceincludes a first region (e.g., first region 660, FIG. 6D) and a secondregion (e.g., second region 662, FIG. 6D) separate from the firstregion.

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the first input (e.g., contact 682, FIGS.6C-6H) corresponds to movement only in the first region (e.g., firstregion 660, FIGS. 6C-6H).

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the first input (e.g., contact 682, FIGS.6C-6H) corresponds to a swipe from an edge of the touch-sensitivesurface (e.g., touch-sensitive surface 604, FIG. 6A-6H) within the firstregion (e.g., first region 660, FIGS. 6C-6H).

In accordance with some embodiments, the multi-view navigation criteriaincludes a determination that the first input (e.g., contact 682, FIGS.6C-6H) corresponds to a swipe that starts in the first region (e.g.,first region 660, FIGS. 6C-6H) and transitions into the second region(e.g., second region 662, FIGS. 6C-6H).

In accordance with some embodiments, the multi-view navigation criteriafurther includes determining that the first input corresponds to acontact (e.g., contact 682, FIGS. 6C-6H) that decelerates within thesecond region (e.g., second region 662, FIGS. 6C-6H).

In accordance with some embodiments, the contact decelerates by at leasta minimum amount within the second region (e.g., second region 662,FIGS. 6C-6H).

In accordance with some embodiments, the multi-view navigation criteriaincludes a determination that the contact (e.g., contact 682, FIGS.6C-6H) has remained in the second region (e.g., second region 662, FIGS.6C-6H) of the touch-sensitive surface (e.g., touch-sensitive surface604, FIG. 6A-6H) for a period of time meeting or exceeding a timethreshold.

In accordance with some embodiments, method 700 determines a viewseparation value based on the period of time, wherein the viewnavigation operation includes navigating from the first view (e.g.,first view 606, FIG. 6) to a third view (e.g., third view 610, FIG. 6)that is separated from the first view by a number of views in thesequence of views that is equal to the view separation value.

In accordance with some embodiments, the view separation value isdetermined based on one or more criteria selected from the groupconsisting of a view time parameter, a pattern of view movement, anapplication process category, or a view history.

In accordance with some embodiments, the view navigation operationincludes navigating from the first view (e.g., first view 606, FIG. 6)to the third view (e.g., third view 610, FIG. 6) that is separated fromthe first view (e.g., first view 606, FIG. 6) by a number of views inthe sequence of view that is equal to the view separation value.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) precedes the first view (e.g., first view 606, FIG. 6) inthe sequence of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) succeeds the first view (e.g., first view 606, FIG. 6) inthe sequence of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) is separated from the first view (e.g., first view 606,FIG. 6) by a predetermined number of views in the sequence of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) is separated from the first view (e.g., first view 606,FIG. 6) by a percentage of views in the sequence of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) is an initial view in the sequence of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) is a last view in the sequence of views.

In accordance with some embodiments, the sequence of views comprise partof a hierarchy of views, the hierarchy of views including one or morenodes.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) in the sequence of views is a node in the hierarchy ofviews.

In accordance with some embodiments, the first view (e.g., first view606, FIG. 6) is a second node in the hierarchy of views.

In accordance with some embodiments, the third view (e.g., third view610, FIG. 6) is a nearest node of the hierarchy that precedes the firstview (e.g., first view 606, FIG. 6).

In accordance with some embodiments, method 700 includes, further inaccordance with a determination that the movement of the contact (e.g.,contact 682, FIGS. 6C-6H) meets multi-view navigation criteria,displaying a stacked view representation of a plurality of portions eachcorresponding to a view of the one or more views separating the firstview from the third view, the plurality of portions including: a firstportion representing a first view of the one or more views separatingthe first view from the third view, and a second portion representing asecond view of the one or more views separating the first view from thethird view, different than the first view of the one or more viewsseparating the first view from the third view.

In accordance with some embodiments, wherein displaying the stacked viewrepresentation includes: displaying the first portion of the stackedview representation prior to displaying the second portion of thestacked view representation.

In accordance with some embodiments, the number of portions in theplurality of portions is less than the number of views of the one ormore views separating the first view from the third view.

In accordance with some embodiments, wherein the first portion and thesecond portion of the stacked view representation are displayed at anangle with respect to a vertical axis.

In accordance with some embodiments, method 700 includes, afterdisplaying the stacked view representation, determining whether astacked view representation deconstruction criteria is met, inaccordance with a determination that the stacked view representationdeconstruction criteria is met, ceasing to display the stacked viewrepresentation.

In accordance with some embodiments, wherein ceasing to display thestacked view representation comprises ceasing to display the secondportion of the stacked view representation prior to ceasing to displaythe first portion of the stacked view representation.

In accordance with some embodiments, wherein the stacked viewrepresentation deconstruction criteria includes: after preparing toperform the view navigation operation, determining that further movementof the contact meets the single-view navigation criteria.

In accordance with some embodiments, FIG. 8 shows an exemplaryfunctional block diagram of an electronic device 800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 800 are configured to perform the techniques described above. Thefunctional blocks of the device 800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 8 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

In accordance with some embodiments, FIG. 8 shows an exemplaryfunctional block diagram of an electronic device 800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 800 are configured to perform the techniques described above. Thefunctional blocks of the device 800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 8 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 8, an electronic device 800 includes a display unit802, a touch-sensitive surface unit 804, and a processing unit 806coupled to the display unit 802 and the touch-sensitive surface unit804. In some embodiments, the processing unit 806 includes a receivingunit 808, preparing unit 810, navigating unit 812, performing unit 814,and determining unit 816.

The processing unit 806 is configured to: display (e.g., using displayunit 802), a first view in a sequence of views; while displaying thefirst view, receive (e.g., using receiving unit 808) an inputcorresponding to a movement of a contact on the touch-sensitive surfacefrom a first position to a second position; while continuing to detectthe contact on the touch-sensitive surface, and in response to receivingthe input, prepare (e.g., using preparing unit 810) to perform a viewnavigation operation, wherein: in accordance with a determination thatthe movement of the contact meets single-view navigation criteria, theview navigation operation includes navigating (e.g., using navigatingunit 812) from the first view to a second view that is adjacent to thefirst view in the sequence of views; and in accordance with adetermination that the movement of the contact meets multi-viewnavigation criteria, the view navigation operation includes navigating(e.g., using navigating unit 812) from the first view to a third viewthat is separated from the first view by one or more views in thesequence of views.

In accordance with some embodiments, processing unit 806 is furtherconfigured to, after preparing to perform the view navigation operation,receive a second input corresponding to liftoff of the contact from thetouch-sensitive surface; in response to receiving the second input,perform (e.g., using performing unit 814) the view navigation operation.

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the multi-view navigation criteria is not met.

In accordance with some embodiments, the touch-sensitive surfaceincludes a first region and a second region separate from the firstregion.

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the first input corresponds to movement onlyin the first region.

In accordance with some embodiments, the single-view navigation criteriaincludes determining that the first input corresponds to a swipe from anedge of the touch-sensitive surface within the first region.

In accordance with some embodiments, the multi-view navigation criteriaincludes a determination that the first input corresponds to a swipethat starts in the first region and transitions into the second region.

In accordance with some embodiments, the multi-view navigation criteriafurther includes determining that the first input corresponds to acontact that decelerates within the second region.

In accordance with some embodiments, the contact decelerates by at leasta minimum amount within the second region.

In accordance with some embodiments, the multi-view navigation criteriaincludes a determination that the contact has remained in the secondregion of the touch-sensitive surface for a period of time meeting orexceeding a time threshold.

In accordance with some embodiments, processing unit 806 is furtherconfigured to determine (e.g., using determining unit 816) a viewseparation value based on the period of time, wherein the viewnavigation operation includes navigating from the first view to a thirdview that is separated from the first view by a number of views in thesequence of views that is equal to the view separation value.

In accordance with some embodiments, the view separation value isdetermined based on one or more criteria selected from the groupconsisting of a view time parameter, a pattern of view movement, anapplication process category, or a view history.

In accordance with some embodiments, the view navigation operationincludes navigating from the first view to the third view that isseparated from the first view by a number of views in the sequence ofview that is equal to the view separation value.

In accordance with some embodiments, the third view precedes the firstview in the sequence of views.

In accordance with some embodiments, the third view succeeds the firstview in the sequence of views.

In accordance with some embodiments, the third view is separated fromthe first view by a predetermined number of views in the sequence ofviews.

In accordance with some embodiments, the third view is separated fromthe first view by a percentage of views in the sequence of views.

In accordance with some embodiments, the third view is an initial viewin the sequence of views.

In accordance with some embodiments, the third view is a last view inthe sequence of views.

In accordance with some embodiments, the sequence of views comprise partof a hierarchy of views, the hierarchy of views including one or morenodes.

In accordance with some embodiments, the third view in the sequence ofviews is a node in the hierarchy of views.

In accordance with some embodiments, the first view is a second node inthe hierarchy of views.

In accordance with some embodiments, the third view is a nearest node ofthe hierarchy that precedes the first view.

In accordance with some embodiments, processing unit 806 is configuredto, further in accordance with a determination that the movement of thecontact meets multi-view navigation criteria, display a stacked viewrepresentation of a plurality of portions each corresponding to a viewof the one or more views separating the first view from the third view,the plurality of portions including: a first portion representing afirst view of the one or more views separating the first view from thethird view, and a second portion representing a second view of the oneor more views separating the first view from the third view, differentthan the first view of the one or more views separating the first viewfrom the third view.

In accordance with some embodiments, wherein to display the stacked viewrepresentation, the processing unit 806 is further configured to displaythe first portion of the stacked view representation prior to displayingthe second portion of the stacked view representation.

In accordance with some embodiments, the number of portions in theplurality of portions is less than the number of views of the one ormore views separating the first view from the third view.

In accordance with some embodiments, wherein the first portion and thesecond portion of the stacked view representation are displayed at anangle with respect to a vertical axis.

In accordance with some embodiments, processing unit 806 is furtherconfigured to, after displaying the stacked view representation,determine whether a stacked view representation deconstruction criteriais met, in accordance with a determination that the stacked viewrepresentation deconstruction criteria is met, cease (e.g., usingdisplay unit 802) to display the stacked view representation.

In accordance with some embodiments, wherein to cease display of thestacked view representation, the processing unit 806 is furtherconfigured to cease display of the second portion of the stacked viewrepresentation prior to ceasing to display the first portion of thestacked view representation.

In accordance with some embodiments, wherein the stacked viewrepresentation deconstruction criteria includes: after preparing toperform the view navigation operation, determine that further movementof the contact meets the single-view navigation criteria.

The operations described above with reference to FIG. 7 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 8. Forexample, displaying operation 702, receiving operation 704, preparingoperation 706, determining operation 708 and navigating operations 710and/or 712, can optionally be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 can optionally utilize or calldata updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device, the one or more programs including instructionswhich, when executed by the one or more processors, cause the electronicdevice to: display a first view in a sequence of views; while displayingthe first view, receive an input corresponding to a movement of acontact on a touch-sensitive surface from a first position to a secondposition; while continuing to detect the contact on the touch-sensitivesurface, and in response to receiving the input, prepare to perform aview navigation operation, wherein: in accordance with a determinationthat the movement of the contact meets single-view navigation criteria,the view navigation operation includes navigation from the first view toa second view that is adjacent to the first view in the sequence ofviews; and in accordance with a determination that the movement of thecontact meets multi-view navigation criteria, the view navigationoperation includes navigation from the first view to a third view thatis separated from the first view by one or more views in the sequence ofviews.
 2. The non-transitory computer-readable storage medium of claim1, wherein the one or more programs include instructions which cause theelectronic device to: after preparing to perform the view navigationoperation, receive a second input corresponding to liftoff of thecontact from the touch-sensitive surface; in response to receiving thesecond input, perform the view navigation operation.
 3. Thenon-transitory computer-readable storage medium of claim 1, wherein thesingle-view navigation criteria includes a determination that themulti-view navigation criteria is not met.
 4. The non-transitorycomputer-readable storage medium of claim 1, wherein the touch-sensitivesurface includes a first region and a second region separate from thefirst region.
 5. The non-transitory computer-readable storage medium ofclaim 4, wherein the single-view navigation criteria includes adetermination that the first input corresponds to movement only in thefirst region.
 6. The non-transitory computer-readable storage medium ofclaim 4, wherein the single-view navigation criteria includes adetermination that the first input corresponds to a swipe from an edgeof the touch-sensitive surface within the first region.
 7. Thenon-transitory computer-readable storage medium of claim 4, wherein themulti-view navigation criteria includes a determination that the firstinput corresponds to a swipe that starts in the first region andtransitions into the second region.
 8. The non-transitorycomputer-readable storage medium of claim 4, wherein the multi-viewnavigation criteria includes a determination that the first inputcorresponds to a contact that decelerates within the second region. 9.The non-transitory computer-readable storage medium of claim 8, whereinthe contact decelerates by at least a minimum amount within the secondregion
 10. The non-transitory computer-readable storage medium of claim4, wherein the multi-view navigation criteria includes a determinationthat the contact has remained in the second region of thetouch-sensitive surface for a period of time meeting or exceeding a timethreshold.
 11. The non-transitory computer-readable storage medium ofclaim 10, wherein the one or more programs include instructions whichcause the electronic device to: determine a view separation value basedon the period of time.
 12. The non-transitory computer-readable storagemedium of claim 11, wherein the view separation value is determinedbased on one or more criteria selected from the group consisting of aview time parameter, a pattern of view movement, an application processcategory, or a view history.
 13. The non-transitory computer-readablestorage medium of claim 12, wherein the view navigation operationincludes navigating from the first view to a third view that isseparated from the first view by a number of views in the sequence ofview that is equal to the view separation value.
 14. The non-transitorycomputer-readable storage medium of claim 1, wherein the third viewprecedes the first view in the sequence of views.
 15. The non-transitorycomputer-readable storage medium of claim 1, wherein the third viewsucceeds the first view in the sequence of views.
 16. The non-transitorycomputer-readable storage medium of claim 1, wherein the third view isseparated from the first view by a predetermined number of views in thesequence of views.
 17. The non-transitory computer-readable storagemedium of claim 1, wherein the third view is separated from the firstview by a percentage of views in the sequence of views.
 18. Thenon-transitory computer-readable storage medium of claim 1, wherein thethird view is an initial view in the sequence of views.
 19. Thenon-transitory computer-readable storage medium of claim 1, wherein thethird view is a last view in the sequence of views.
 20. Thenon-transitory computer-readable storage medium of claim 1, wherein thesequence of views include part of a hierarchy of views, the hierarchy ofviews including one or more nodes.
 21. The non-transitorycomputer-readable storage medium of claim 20, wherein the third view inthe sequence of views is a node in the hierarchy of views.
 22. Thenon-transitory computer-readable storage medium of claim 21, wherein thefirst view is a second node in the hierarchy of views.
 23. Thenon-transitory computer-readable storage medium of claim 22, wherein thethird view is a nearest node of the hierarchy that precedes the firstview.
 24. The non-transitory computer-readable storage medium of claim1, wherein the one or more programs include instructions which cause theelectronic device to: further in accordance with a determination thatthe movement of the contact meets multi-view navigation criteria,display a stacked view representation of a plurality of portions eachcorresponding to a view of the one or more views separating the firstview from the third view, the plurality of portions including: a firstportion representing a first view of the one or more views separatingthe first view from the third view, and a second portion representing asecond view of the one or more views separating the first view from thethird view, different than the first view of the one or more viewsseparating the first view from the third view.
 25. The non-transitorycomputer-readable storage medium of claim 24, wherein to display thestacked view representation, the one or more programs includeinstructions which cause the electronic device to: display the firstportion of the stacked view representation prior to displaying thesecond portion of the stacked view representation
 26. The non-transitorycomputer-readable storage medium of claim 24, wherein the number ofportions in the plurality of portions is less than the number of viewsof the one or more views separating the first view from the third view.27. The non-transitory computer-readable storage medium of claim 24,wherein the first portion and the second portion of the stacked viewrepresentation are displayed at an angle with respect to a vertical axis28. The non-transitory computer-readable storage medium of claim 24,wherein the one or more programs include instructions which cause theelectronic device to: after displaying the stacked view representation,determine whether a stacked view representation deconstruction criteriais met, in accordance with a determination that the stacked viewrepresentation deconstruction criteria is met, cease to display thestacked view representation.
 29. The non-transitory computer-readablestorage medium of claim 28, wherein to ceasing display of the stackedview representation, the one or more programs include instructions whichcause the electronic device to cease display of the second portion ofthe stacked view representation prior to ceasing to display the firstportion of the stacked view representation.
 30. The non-transitorycomputer-readable storage medium of claim 28, wherein the stacked viewrepresentation deconstruction criteria includes: after preparing toperform the view navigation operation, determine that further movementof the contact meets the single-view navigation criteria.
 31. A method,comprising: at an electronic device including a display and atouch-sensitive surface: displaying, on the display, a first view in asequence of views; while displaying the first view, receiving an inputcorresponding to a movement of a contact on a touch-sensitive surfacefrom a first position to a second position; while continuing to detectthe contact on the touch-sensitive surface, and in response to receivingthe input, preparing to perform a view navigation operation, wherein: inaccordance with a determination that the movement of the contact meetssingle-view navigation criteria, the view navigation operation includesnavigating from the first view to a second view that is adjacent to thefirst view in the sequence of views; and in accordance with adetermination that the movement of the contact meets multi-viewnavigation criteria, the view navigation operation includes navigatingfrom the first view to a third view that is separated from the firstview by one or more views in the sequence of views.
 32. An electronicdevice comprising: one or more processors; memory; a display and atouch-sensitive surface each coupled to the one or more processors andmemory; and one or more programs stored in memory, the one or moreprograms including instructions for: displaying, on the display, a firstview in a sequence of views; while displaying the first view, receivingan input corresponding to a movement of a contact on the touch-sensitivesurface from a first position to a second position; while continuing todetect the contact on the touch-sensitive surface, and in response toreceiving the input, preparing to perform a view navigation operation,wherein: in accordance with a determination that the movement of thecontact meets single-view navigation criteria, the view navigationoperation includes navigating from the first view to a second view thatis adjacent to the first view in the sequence of views; and inaccordance with a determination that the movement of the contact meetsmulti-view navigation criteria, the view navigation operation includesnavigating from the first view to a third view that is separated fromthe first view by one or more views in the sequence of views.